Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

0155

reference: 723-tree-1
name: 0155
tree-preservation-order: undefined
723-tpo-1
uprn
address-text
point: POINT (-0.989772 50.867552)
geometry: MULTIPOLYGON (((-0.989729 50.867548,-0.989731 50.867556,-0.989737 50.867564,-0.989746 50.867570,-0.989758 50.867574,-0.989771 50.867575,-0.989784 50.867574,-0.989796 50.867570,-0.989806 50.867564,-0.989812 50.867557,-0.989814 50.867549,-0.989812 50.867540,-0.989807 50.867533,-0.989797 50.867527,-0.989786 50.867523,-0.989772 50.867521,-0.989747 50.867526,-0.989738 50.867532,-0.989731 50.867540,-0.989729 50.867548)))
notes
felled-date
entry-date: 2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL